Skip to content

[WIP] test/e2e: add optional Azure Linux 4 cluster e2e test#6312

Draft
mboersma wants to merge 2 commits into
kubernetes-sigs:mainfrom
mboersma:e2e-azl4
Draft

[WIP] test/e2e: add optional Azure Linux 4 cluster e2e test#6312
mboersma wants to merge 2 commits into
kubernetes-sigs:mainfrom
mboersma:e2e-azl4

Conversation

@mboersma
Copy link
Copy Markdown
Contributor

@mboersma mboersma commented May 14, 2026 •
edited
Loading

What type of PR is this?

/kind feature

What this PR does / why we need it:

Adds a new [OPTIONAL] e2e Context that builds a 3+2 HA cluster from the experimental capi-azurelinux-4-gen2 shared community gallery image, mirroring the existing Azure Linux 3 spec.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Special notes for your reviewer:

See also kubernetes-sigs/image-builder#2014

The second commit is a temporary PContext skip of the other [OPTIONAL] specs so the e2e-optional presubmit exercises only the new AZL4 spec from this draft PR. It will be dropped before merge.

TODOs:

  • squashed commits
  • includes documentation
  • adds unit tests
  • cherry-pick candidate

Release note:

test/e2e: add optional Azure Linux 4 cluster e2e test

@k8s-ci-robot
Copy link
Copy Markdown
Contributor

k8s-ci-robot commented May 14, 2026

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@k8s-ci-robot k8s-ci-robot added release-note Denotes a PR that will be considered when it comes time to generate release notes. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. kind/feature Categorizes issue or PR as related to a new feature. labels May 14, 2026
@k8s-ci-robot k8s-ci-robot requested review from marosset and nojnhuh May 14, 2026 21:18
@k8s-ci-robot
Copy link
Copy Markdown
Contributor

k8s-ci-robot commented May 14, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign neolit123 for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels May 14, 2026
@mboersma mboersma changed the title test/e2e: add optional Azure Linux 4 cluster e2e test [WIP] test/e2e: add optional Azure Linux 4 cluster e2e test May 14, 2026
@codecov
Copy link
Copy Markdown

codecov Bot commented May 14, 2026 •
edited
Loading

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 43.84%. Comparing base (2ea3260) to head (e4868e7).
⚠️ Report is 8 commits behind head on main.

Additional details and impacted files 
@@           Coverage Diff           @@
##             main    #6312   +/-   ##
=======================================
  Coverage   43.84%   43.84%           
=======================================
  Files         289      289           
  Lines       25346    25346           
=======================================
  Hits        11114    11114           
  Misses      13458    13458           
  Partials      774      774

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@mboersma
Copy link
Copy Markdown
Contributor Author

mboersma commented May 14, 2026

/test pull-cluster-api-provider-azure-e2e-optional

@mboersma
Copy link
Copy Markdown
Contributor Author

mboersma commented May 14, 2026

/test pull-cluster-api-provider-azure-e2e-optional

(Failure was #5690)

@mboersma
Copy link
Copy Markdown
Contributor Author

mboersma commented May 18, 2026

/retest

New k8s 1.35.3 image built.

@mboersma
Copy link
Copy Markdown
Contributor Author

mboersma commented May 18, 2026

✅ Proof that all nodes were provisioned from the Azure Linux 4 image, from the successful pull-cluster-api-provider-azure-e2e-optional run (build 2056485910723170304). Values come from per-node kubectl describe node output captured under artifacts/clusters/capz-e2e-l1dqji-azl4/nodes/<machine>/node-describe.txt:

Node Role OS Image Kernel Kubelet
capz-e2e-l1dqji-azl4-control-plane-jkkg7 control-plane Azure Linux 4.0 (Cloud Variant Beta) 6.18.29-1.1.azl4.x86_64 v1.35.3
capz-e2e-l1dqji-azl4-control-plane-kshsg control-plane Azure Linux 4.0 (Cloud Variant Beta) 6.18.29-1.1.azl4.x86_64 v1.35.3
capz-e2e-l1dqji-azl4-control-plane-sgcqc control-plane Azure Linux 4.0 (Cloud Variant Beta) 6.18.29-1.1.azl4.x86_64 v1.35.3
capz-e2e-l1dqji-azl4-md-0-b7xz8-bgmcr worker Azure Linux 4.0 (Cloud Variant Beta) 6.18.29-1.1.azl4.x86_64 v1.35.3
capz-e2e-l1dqji-azl4-md-0-b7xz8-tvxnr worker Azure Linux 4.0 (Cloud Variant Beta) 6.18.29-1.1.azl4.x86_64 v1.35.3

All 5 nodes — 3 control plane + 2 workers — registered with OS Image: Azure Linux 4.0 (Cloud Variant Beta) and kernel 6.18.29-1.1.azl4.x86_64 (the .azl4 suffix confirms the kernel package came from the Azure Linux 4 repo). Container runtime was containerd 2.2.2 on every node. Both values are reported by kubelet itself, so they reflect what is actually running on each VM.

@mboersma
Copy link
Copy Markdown
Contributor Author

mboersma commented May 19, 2026

/override pull-cluster-api-provider-azure-apiversion-upgrade

(Just for optics--this will remain a WIP for a while but that test isn't directly relevant currently.)

@k8s-ci-robot
Copy link
Copy Markdown
Contributor

k8s-ci-robot commented May 19, 2026

@mboersma: Overrode contexts on behalf of mboersma: pull-cluster-api-provider-azure-apiversion-upgrade

Details

In response to this:

/override pull-cluster-api-provider-azure-apiversion-upgrade

(Just for optics--this will remain a WIP for a while but that test isn't directly relevant currently.)

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@marosset marosset Awaiting requested review from marosset

@nojnhuh nojnhuh Awaiting requested review from nojnhuh

Assignees

No one assigned

Labels

cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. kind/feature Categorizes issue or PR as related to a new feature. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.

Projects

CAPZ Planning
Status: Todo

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@mboersma @k8s-ci-robot